Defining CVS Modules

All those SNiFF+ projects that you want to be able to access as "master modules" need to be defined in your CVS modules file. A "master module" is one that is accessible by the CVS Module commands. The connection between a SNiFF+ project and a CVS module is by its name: a CVS module name is always constructed by removing the

.shared extension from the corresponding SNiFF+ project name. So, for example, the SNiFF+ Project complex.shared must be assigned the CVS module complex no matter where in the directory hierarchy this module resides!

You can easily edit the modules file by choosing CVS Admin > Edit modules File.

In the modules file, lines starting with a hash sign (#) are comments and can be ignored. Your new entries should be added at the end of the modules file.

Each line contains the name of a module and, separated by whitespace, it's location relative to the repository root.

If you imported your entire Working Environment into "." (= the repository root) before and want to be able to access all modules directly, this is what you should enter into your modules file:

complex | complex
complexlib | complex/complexlib
iolib | complex/iolib

If you imported your project into

sniff/examples , this is what you would enter:

complex | sniff/examples/complex
complexlib | sniff/examples/complex/complexlib
iolib | sniff/examples/complex/iolib

So the modules file provides the connection from SNiFF+ project locations to the repository locations.

Note that since all CVS module commands will work with the given module and all its subdirectories, it is not necessary to assign a CVS module to all SNiFF+ modules. In the example above, it would indeed suffice to define the

complex module only since accessing complex will automatically access iolib and complexlib as well. However, in that case it would not be possible to check out the complexlib module by itself.

For more information about other options in the modules file, please read CVS Manual.